bugsnag: propagate cloud_provider into contextual logging for queued executions#268
Conversation
65d8571 to
3bb4cc1
Compare
|
CC: @yuechao-qin This will allow you to filter errors to Nebius or GKE. |
3bb4cc1 to
faed3ca
Compare
abe0fb0 to
4730f88
Compare
a2974f3 to
410f807
Compare
|
|
||
| from .. import backend_types_sql as bts | ||
|
|
||
| _CLOUD_PROVIDER_ANNOTATION_KEY = "cloud-pipelines.net/orchestration/cloud_provider" |
There was a problem hiding this comment.
nebius_launchers.py has this same exact constant. Would it make sense to create a shared config/model/etc file that both of them reference against? Or some way to not duplicate the variable?
There was a problem hiding this comment.
🤖 Good eye, but the duplication is intentional for now. The tech lead asked us not to commit CLOUD_PROVIDER_ANNOTATION_KEY to the shared common_annotations layer yet — there's an open question about whether a launcher-specific annotation is the right long-term standard, or whether a different annotation design would be better. Once there's consensus, we can consolidate. Until then, keeping it private to each module avoids prematurely locking in the API.
4730f88 to
e6a36dc
Compare
410f807 to
f313191
Compare
Merge activity
|
…executions Adds CLOUD_PROVIDER_ANNOTATION_KEY to common_annotations so the annotation key has a single definition in the OSS layer. In the queued-execution processing span, reads the cloud_provider value from task_spec annotations (already in memory) and adds it to the contextual logging context when present. The existing _before_notify hook then includes it automatically in the tangle_context tab on every Bugsnag event raised during that execution's processing.
f313191 to
964652e
Compare


No description provided.